-
Notifications
You must be signed in to change notification settings - Fork 748
Qualcomm AI Engine Direct - Fixed the wrong size for memmove in kv_manager #14685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14685
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 2 Unrelated FailuresAs of commit 9ea1583 with merge base ebf4c12 ( NEW FAILURE - The following job has failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot cherry-pick --onto release/1.0 -c regression |
This PR needs a
|
|
Can you share more details in terms of what we're fixing? |
| // copy from first dimension | ||
| for (int i = 0; i < metadata_.head_dim; i++) { | ||
| std::memmove(k_cache_in_write_ptr, k_cache_in_read_ptr, dst_cache_num); | ||
| std::memmove( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh I see, makes sense
As title.
cc: @haowhsu-quic , @winskuo-quic